Skip to content

Conversation

@dubielzyk-expensify
Copy link
Contributor

@dubielzyk-expensify dubielzyk-expensify commented Nov 30, 2025

Explanation of Change

Fixes typo where report titles was referred to as report names

Fixed Issues

$
PROPOSAL:

Tests

  • Verify that no errors appear in the JS console

Offline tests

QA Steps

  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I verified there are no new alerts related to the canBeMissing param for useOnyx
  • I followed proper code patterns (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
      • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
    • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
    • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
    • I verified the JSDocs style guidelines (in STYLE.md) were followed
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
  • I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
  • I verified that if a function's arguments changed that all usages have also been updated correctly
  • If any new file was added I verified that:
    • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
  • If new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari dev new expensify com_8082_workspaces_6C7D8C5F326720ED_reports(iPhone 15 Pro)
MacOS: Chrome / Safari dev new expensify com_8082_workspaces_6C7D8C5F326720ED_reports(Screenshot (Desktop))

@dubielzyk-expensify dubielzyk-expensify requested review from a team as code owners November 30, 2025 23:03
@melvin-bot melvin-bot bot requested review from joekaufmanexpensify and removed request for a team November 30, 2025 23:03
@melvin-bot
Copy link

melvin-bot bot commented Nov 30, 2025

Concierge reviewer checklist:

  • I have verified the accuracy of the article
    • The article is within a hub that makes sense, and the navigation is correct
    • All processes, screenshots, and examples align with current product behavior.
    • All links within the doc have been verified for correct destination and functionality.
  • I have verified the readability of the article
    • The article's language is clear, concise, and free of jargon.
    • The grammar, spelling, and punctuation are correct.
    • The article contains at least one image, or that an image is not necessary
  • I have verified the formatting of the article
    • The article has consistent formatting (headings, bullet points, etc.) with other HelpDot articles and that aligns with the HelpDot formatting standards.
    • The article has proper text spacing and breaks for readability.
  • I have verified the article has the appropriate tone and style
    • The article's tone is professional, friendly, and suitable for the target audience.
    • The article's tone, terminology, and voice are consistent throughout.
  • I have verified the overall quality of the article
    • The article is not missing any information, nor does it contain redundant information.
    • The article fully addresses user needs.
  • I have verified that all requested improvements have been addressed

For more detailed instructions on completing this checklist, see How do I review a HelpDot PR as a Concierge Team member?

cc @brianlee-expensify

@melvin-bot
Copy link

melvin-bot bot commented Nov 30, 2025

@jasperhuangg @brianlee-expensify One of you needs to copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@melvin-bot melvin-bot bot removed the request for review from a team November 30, 2025 23:03
@OSBotify
Copy link
Contributor

🦜 Polyglot Parrot! 🦜

Squawk! Looks like you added some shiny new English strings. Allow me to parrot them back to you in other tongues:

View the translation diff
diff --git a/src/languages/de.ts b/src/languages/de.ts
index 91d55fdf..fdcd088d 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -4987,7 +4987,7 @@ ${
             customNameWorkspaceNameExample: 'Workspace-Name: {report:workspacename}',
             customNameReportIDExample: 'Report-ID: {report:id}',
             customNameTotalExample: 'Gesamt: {report:total}.',
-            preventMembersFromChangingCustomNamesTitle: 'Verhindern Sie, dass Mitglieder benutzerdefinierte Berichtsnamen ändern',
+            preventMembersFromChangingCustomNamesTitle: 'Verhindern, dass Mitglieder benutzerdefinierte Berichtstitel ändern',
         },
         reportFields: {
             addField: 'Feld hinzufügen',
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index de1d6428..4a8016be 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -4999,7 +4999,7 @@ ${
             customNameWorkspaceNameExample: "Nom de l'espace de travail : {report:workspacename}",
             customNameReportIDExample: 'Report ID : {report:id}',
             customNameTotalExample: 'Total : {report:total}.',
-            preventMembersFromChangingCustomNamesTitle: 'Empêcher les membres de modifier les noms des rapports personnalisés',
+            preventMembersFromChangingCustomNamesTitle: 'Empêcher les membres de modifier les titres de rapports personnalisés',
         },
         reportFields: {
             addField: 'Ajouter un champ',
diff --git a/src/languages/it.ts b/src/languages/it.ts
index 7e026ab3..71d815b2 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -4976,7 +4976,7 @@ ${
             customNameWorkspaceNameExample: "Nome dell'area di lavoro: {report:workspacename}",
             customNameReportIDExample: 'Report ID: {report:id}',
             customNameTotalExample: 'Totale: {report:total}.',
-            preventMembersFromChangingCustomNamesTitle: 'Impedisci ai membri di modificare i nomi dei report personalizzati',
+            preventMembersFromChangingCustomNamesTitle: 'Impedisci ai membri di modificare i titoli dei report personalizzati',
         },
         reportFields: {
             addField: 'Aggiungi campo',
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index e1331418..a634b407 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -4932,7 +4932,7 @@ ${
             customNameWorkspaceNameExample: 'ワークスペース名: {report:workspacename}',
             customNameReportIDExample: 'Report ID: {report:id}',
             customNameTotalExample: '合計: {report:total}.',
-            preventMembersFromChangingCustomNamesTitle: 'メンバーがカスタムレポート名を変更するのを防ぐ',
+            preventMembersFromChangingCustomNamesTitle: 'メンバーがカスタムレポートのタイトルを変更するのを防ぐ',
         },
         reportFields: {
             addField: 'フィールドを追加',
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index f57ae877..50bc1f12 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -4967,7 +4967,7 @@ ${
             customNameWorkspaceNameExample: 'Werkruimte naam: {report:workspacename}',
             customNameReportIDExample: 'Report ID: {report:id}',
             customNameTotalExample: 'Totaal: {report:total}.',
-            preventMembersFromChangingCustomNamesTitle: 'Voorkom dat leden aangepaste rapportnamen wijzigen',
+            preventMembersFromChangingCustomNamesTitle: 'Voorkom dat leden aangepaste rapporttitels wijzigen',
         },
         reportFields: {
             addField: 'Veld toevoegen',
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index 1cab38d9..d1e24d58 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -4957,7 +4957,7 @@ ${
             customNameWorkspaceNameExample: 'Nazwa przestrzeni roboczej: {report:workspacename}',
             customNameReportIDExample: 'Report ID: {report:id}',
             customNameTotalExample: 'Suma: {report:total}.',
-            preventMembersFromChangingCustomNamesTitle: 'Uniemożliw członkom zmianę nazw raportów niestandardowych',
+            preventMembersFromChangingCustomNamesTitle: 'Uniemożliw członkom zmianę niestandardowych tytułów raportów',
         },
         reportFields: {
             addField: 'Dodaj pole',
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index 7d1cb608..aca82a8d 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -4960,7 +4960,7 @@ ${
             customNameWorkspaceNameExample: 'Nome do espaço de trabalho: {report:workspacename}',
             customNameReportIDExample: 'ID do Relatório: {report:id}',
             customNameTotalExample: 'Total: {report:total}.',
-            preventMembersFromChangingCustomNamesTitle: 'Impedir que os membros alterem os nomes dos relatórios personalizados',
+            preventMembersFromChangingCustomNamesTitle: 'Impedir que membros alterem os títulos personalizados de relatórios',
         },
         reportFields: {
             addField: 'Adicionar campo',
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index 3bb1d2e2..082d928d 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -4866,7 +4866,7 @@ ${
             customNameWorkspaceNameExample: '工作区名称:{report:workspacename}',
             customNameReportIDExample: '报告 ID: {report:id}',
             customNameTotalExample: '总计:{report:total}。',
-            preventMembersFromChangingCustomNamesTitle: '禁止成员更改自定义报告名称',
+            preventMembersFromChangingCustomNamesTitle: '禁止成员修改自定义报告标题',
         },
         reportFields: {
             addField: '添加字段',

Note

You can apply these changes to your branch by copying the patch to your clipboard, then running pbpaste | git apply 😉

2. Click to open the formula editor.
3. Use the formula list below to build your title.
4. (Optional) Enable **Prevent members from changing custom report names** to lock naming rules.
4. (Optional) Enable **Prevent members from changing custom report titles** to lock naming rules.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good fix! However, there are other instances of "report names" in this document (line 29) that should also be changed to "report titles" for consistency.

@github-actions
Copy link
Contributor

HelpDot Documentation Review

Overall Assessment

This PR contains a minor but important terminology correction, changing "report names" to "report titles" across one documentation file and the corresponding language file. The change improves consistency and accuracy throughout the documentation by using the correct technical term that aligns with the feature name and UI elements.

Scores Summary

  • Readability: 9/10 - The documentation is well-structured with clear headings, concise instructions, and helpful examples. The step-by-step format makes it easy to follow. Minor deduction for some inconsistent terminology usage in line 29 where "report names" still appears (though this may be intentional as it refers to a general concept rather than the specific feature).

  • AI Readiness: 8/10 - Strong metadata with descriptive title, keywords, and description. Clear navigation paths and well-structured heading hierarchy using only # and ##. The formula reference tables provide excellent structured data. However, there's room for improvement in providing more context around technical terms like "base 62 representation" (line 44) which could be confusing without explanation.

  • Style Compliance: 9/10 - Excellent adherence to Expensify documentation standards with proper terminology ("workspace" used consistently), clear navigation paths in the expected format, and proper markdown formatting throughout. The use of code blocks for formulas and consistent table formatting demonstrates strong style compliance.

Key Findings

  • Positive: The terminology fix directly addresses a consistency issue where the feature is called "Report Titles" but documentation referred to "report names"
  • Positive: The documentation is comprehensive, including formula reference tables, date format options, and advanced functions
  • Positive: Good use of examples throughout (lines 22-23, 96-99) to illustrate concepts
  • Minor Issue: Line 29 still contains "Custom report names" which should potentially be "Custom report titles" for consistency (though this appears in a conceptual explanation context)

Recommendations

  1. High Priority: Review line 29 to determine if "Custom report names" should also be changed to "Custom report titles" for complete consistency
  2. Medium Priority: Consider adding a brief explanation for technical terms like "base 62 representation" (line 44) to improve accessibility
  3. Low Priority: Consider adding a brief introductory sentence to the "Date Format Options" section explaining when/where these formats apply

Files Reviewed

  • docs/articles/new-expensify/reports-and-expenses/Customize-and-Enforce-Report-Titles.md - Terminology fix applied (1 instance corrected, 1 potential instance remains on line 29)
  • src/languages/en.ts - Corresponding UI text updated to match

Note: This is a straightforward terminology correction that improves documentation accuracy and consistency.

@github-actions github-actions bot changed the title Fix typo [No QA] Fix typo Nov 30, 2025
@OSBotify
Copy link
Contributor

A preview of your ExpensifyHelp changes have been deployed to https://94038b75.helpdot.pages.dev ⚡️

Updated articles:

@codecov
Copy link

codecov bot commented Nov 30, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
see 7 files with indirect coverage changes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants